Scanned list item is used for scanning barcodes. |
Main |
Main screen for creating/amending a Scanned list item | ||||||||
*Question | This is the text “label” that is specifying the information that needs to be entered or the question to be answered. Although this is not necessarily a question in all cases, Question is used as the general term to cover the text shown next to an input field. The text should be as short as possible whilst still being self-explanatory. Over-long questions take up a lot of space on PDA screens with their restricted size, so try and make them concise. This text should be an aid to help guide the user through the screen. Any more explanatory text can be made available as “Auditor’s notes” or “Full question text”. | ||||||||
Mandatory |
Tick this box if the question is mandatory and leave it blank if it is optional. This will depend on whether the answer to this question is critical to the data that is being collected, such as signature to confirm customer acceptance. |
||||||||
Default value |
Enter a value that will be inserted without the user doing anything e.g. '0' (zero) for quantity in a supplies list so that only significant entries need to be entered. Sometimes it is appropriate to use values entered by administrators when setting up a job. In this case, use the syntax: $$[unique name used in job definition] |
||||||||
Maximum length | The longest allowable scan length. | ||||||||
Item to lookup scanned lengths from (enter the 'unique name') | Enter the unique name of the data item that holds the list item that has already been selected and will provide the barcode length for validation purposes. | ||||||||
Unique name of quantity item | Enter the unique name of the quantity item. | ||||||||
Name used to group items that should be validated together | To prevent mistakes, the same barcode cannot be scanned twice. However, to allow for the unusual situation where this might be required, different groups can be set up to be validated separately. | ||||||||
Disallowed scan values (separate with commas) | To further reduce the possibility of manual errors, common disallowed, numerical barcodes can be entered here, separated by commas. Useful entries here would be manufacturers' delivery barcodes. | ||||||||
Formatting |
Formatting options for a Scanned list item. | ||||||||
Number of lines to display | Controls the number of lines shown in the text box, hence the height of the box. Note that this does not affect how much data can be entered in the box because the box will scroll any content. However, it does control the height of the box as shown on the screen. | ||||||||
Full screen width? |
This option is usually used in conjunction with multi-line text boxes, giving the user a full-width long text box in which to enter information. This value overrides any formatting set for the section. |
||||||||
Advanced |
Advanced features of a Scanned list item. | ||||||||
Text snippets list | Select the appropriate list of Text snippets from the drop-down list. These will need to have been prepared in advance. | ||||||||
Auditor's notes |
If you wish to offer the end-user guidance and direction on how to answer a question then use the Auditor’s notes field. This allows you to input any necessary text expanding on the basic question. For the end-user, the auditor’s notes are available via the “right click” option on the device – tap and hold the stylus on the question text. |
||||||||
Don't keep previous result when part of a document lifecycle |
Tick this box if you DO NOT wish data to be collected in this template item to be copied to any jobs created directly from the original form. This is useful for a repeated task (such as booking in/out a rental item or repeated delivery) where the data remains the same but a sign-off is required so this box may be ticked for Date, Surname and Signature. Please note that if a $$transformation$$ option is applied to the newly created job, this setting may be over-ruled. |
||||||||
Full question (for report) |
The question text mentioned above should be framed in such a way as to indicate to the user the information that needs to be input. However, when this information is output on a report via the web site or a PDF additional wording may well be required. Use this field to phrase the original question in a way suitable for the report. |
||||||||
Cross Reference |
This field is output on reports to cross-reference the information with any relevant legislation etc. |
||||||||
Allow multiple results for this field? |
If you wish to have the capability of entering more than one “answer” to a question then you can use this field. If it is checked/ticked then a button will be displayed allowing further responses to be input. The text shown on this button can be specified (see below). |
||||||||
Text on button for adding additional results |
This option is used in conjunction with “Allow multiple results for this field” and specifies the text shown on the button (for example, “Add response” or “Another value"). |
||||||||
*Unique name |
A unique name must exist for everything in a magic5 template. It is so important that magic5 pre-fills the prompt with a non-meaningful name which it will use by default. This does not need to be changed. However, if the data associated with the unique name is to be used elsewhere (for example as part of a calculation, imported or exported, or carried over to a new job), it is helpful to use a meaningful name (such as RefNo, QuantityOrdered, ItemTotal, ContactName, ReasonForReferral) and this meaningful name must be entered before the template is used with real data. If the unique name is changed at a later date, existing data will not be lost but it may no longer be accessible by magic5, in which case it cannot be displayed, used in calculations or exported. It is therefore recommended that this is done only as a last resort and that the original template is duplicated before changes are made - this means that existing data can still be retrieved if necessary. If in any doubt, please contact magic5 support for the best way to deal with this. |
||||||||
|
|||||||||
Item flag |
Template item flags are used to apply display classes to $$template item$$ in a consistent and efficient way. They are set up in a system list called Template item flags and might be given names such as Danger so the text appears in red, Disclaimer for smaller text, Long answer to give extra space to the answer. This means that changing the display class can be done in one place rather than on all template items. |